Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles

ABSTRACT

Systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles are described herein. Exemplary implementations may: manage environment state information maintaining a collaboration environment; obtain role information specifying roles of the users within units of work and projects; update the environment state information based on the role information; effectuate presentation of the collaboration environment based on the environment state information so that access, by the users, to the individual units of work and the individual projects reflects the roles of the users within the units of work and the projects; and/or perform other operations.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to facilitate interaction with a collaboration environment based on assignment of project-level roles.

BACKGROUND

Collaboration environments, sometimes referred to as work management platforms, may enable users to assign projects, tasks, or other assignments to assignees (e.g., other users) to complete. A collaboration environment may comprise an environment in which individual users and/or a virtual team of users does its work and may enable users to work in a more organized and efficient manner. Projects are a way to organize groups of tasks.

SUMMARY

One aspect of the present disclosure relates to a system configured to facilitate interaction with a collaboration environment based on assignment of project-level roles. A project may include one or more units of work subordinate to the project, that make up the project, and/or otherwise support the project. Organizing at the project-level may be difficult for a variety of reasons. For example, it may be difficult to keep track of the multiple units of work that need to be completed, when they should be completed, the assignment of users to the units of work, and the roles of users in those units of work, in order to otherwise maintain control of the project. There has yet to be a concise way to organize workflow on a project-level within an online collaboration environment which differs from the organization of the units of work that that make up a project.

One or more implementations presented herein propose assignment of users to different roles at the project level. The project-level roles may differ from the roles of the users in the individual units of work. For example, a user may be an “owner” of a project, and also an “engineer” for a unit of work that supports the project. Project-level roles may provide users certain permissions and/or privileges at the project-level and/or for individual units of work that make up a project. These permissions and/or privileges may facilitate certain access to the projects and/or units of work that make up the projects. The access may be characterized based on enabling and/or disabling one or more features. The one or more features may include one or more of editing, internal and/or external communication, meeting generation, and/or other features.

One or more implementations of a system to facilitate interaction with a collaboration environment based on assignment of project-level roles may include one or more hardware processors configured by machine-readable instructions and/or other components. Executing the machine-readable instructions may cause the one or more hardware processors to facilitate interaction with a collaboration environment based on assignment of project-level roles. The machine-readable instructions may include one or more computer program components. The one or more computer program components may include one or more of an environment state component, a role management component, a user interface component, and/or other components.

The environment state component may be configured to manage environment state information maintaining a collaboration environment and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may define one or more of work unit records, project records, and/or other records. The work unit records may include work information comprising values of work unit parameters defining units of work managed, created, and/or assigned to the users within the collaboration environment. The project records may include project information comprising values for project parameters associated with projects managed within the collaboration environment.

An individual project may include an individual set of the units of work. An individual set of units of work of an individual project may be subordinate to the individual project, may make up the individual project, and/or may otherwise support the individual project. An individual set of units of work may directly facilitate progress toward fulfillment of an individual project. The individual set of units of work may directly contribute to the progress. By way of non-limiting illustration, a connection between the individual set of units of work and a corresponding individual project may be direct in that completion of at least one of the units of work may have a direct impact on progress toward fulfillment of the individual project. The concept of “direct impact” may mean that completion of the at least one unit of work may cause progress toward fulfillment of individual project based on independent action completed and/or started with respect to the at least one unit of work. Accordingly, completion of individual set of units of work may indicate that the individual project has been completed and/or fulfilled.

The role management component may be configured to obtain role information specifying roles of the users within the units of work and/or within the projects. The roles may convey an expected contribution of the users in completing and/or supporting the units of work and/or the projects. The individual roles of individual users within the units of work may be specified separately from the individual roles of the individual users within the individual projects. By way of non-limiting illustration, a first user may have a first role within a first unit of work, a second role within a first project, and/or other roles within other units of work and/or projects. The first project may include the first unit of work and one or more other units of work.

The environment state component may be configured to update the environment state information based on the role information and/or other information. By way of non-limiting illustration, the work unit parameters may include a work unit role parameter characterizing the individual roles of the individual users with respect to individual units of work. The project parameters include a project role parameter characterizing the individual roles of the individual users with respect to individual projects. By way of non-limiting illustration, a first value of the work unit role parameter for the first unit of work may specify that the first user has the first role within the first unit of work. A second value of the project role parameter for the first project may specify that the first user has the second role within the first project.

The user interface component may be configured to effectuate presentation of the collaboration environment based on the environment state information and/or other information. In some implementations, access by the users to the individual units of work and/or the individual projects may reflect the roles of the users within the units of work and/or the projects.

As used herein, any association (or relation, or reflection, or indication, or correspondency) involving servers, processors, client computing platforms, and/or another entity or object that interacts with any part of the system and/or plays a part in the operation of the system, may be a one-to-one association, a one-to-many association, a many-to-one association, and/or a many-to-many association or N-to-M association (note that N and M may be different numbers greater than 1).

These and other features, and characteristics of the present technology, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to facilitate interaction with a collaboration environment based on assignment of project-level roles, in accordance with one or more implementations.

FIG. 2 illustrates a method to facilitate interaction with a collaboration environment based on assignment of project-level roles, in accordance with one or more implementations.

FIG. 3 illustrates a user interface, in accordance with one or more implementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to facilitate interaction with a collaboration environment based on assignment of project-level roles, in accordance with one or more implementations. A project may include one or more units of work subordinate to the project, that make up the project, and/or otherwise support the project. To organize workflow at the project-level, users may be assigned roles at the project level. The project-level roles may differ from the roles of the users in the individual units of work that make up projects. Project-level roles may provide users certain permissions and/or privileges at the project-level and/or for individual units of work. These permissions and/or privileges may facilitate improved project organization and/or control by enabling and/or disabling access to one or more features available within the collaboration environment.

In some implementations, system 100 may include one or more of one or more servers 102, one or more client computing platforms 104, external resources 126, and/or other components. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture and/or other architectures. Client computing platform(s) 104 may be configured to communicate with other client computing platforms via server(s) 102 and/or according to a peer-to-peer architecture and/or other architectures. Users may access system 100 via client computing platform(s) 104.

Server(s) 102 may include one or more of non-transitory electronic storage 128, one or more processors 130 configured by machine-readable instructions 106, and/or other components. The non-transitory electronic storage 128 may store one or more records and/or other information. Machine-readable instructions 106 may include one or more instruction components. The instruction components may include computer program components. Executing the machine-readable instructions 106 may cause server(s) 102 to facilitate interaction with a collaboration environment based on assignment of project-level roles. The computer program components may include one or more of an environment state component 108, a role management component 110, a user interface component 112, and/or other components.

Environment state component 108 may be configured to manage environment state information and/or other information used in maintaining a collaboration environment. The collaboration environment may be configured to facilitate interaction by users within the collaboration environment. The environment state information may include one or more of user records, work unit records, project records, objective records, and/or other records. The user records may include user information comprising values of user parameters. The work unit records which may include work information comprising values for work unit parameters associated with units of work managed, created, and/or assigned within the collaboration environment. The project records may include project information including values for project parameters associated with projects managed within the collaboration environment. An individual project may include an individual set of the units of work.

The user information in the user records may include values of user parameters. The values of the user parameters may be organized in user records corresponding to users interacting with and/or viewing the collaboration environment. The values of the user parameters may include information describing the users, their actions within the collaboration environment, their settings, and/or other user information; and/or metadata associated with the users, their actions within the environment, their settings, and/or other user information. Individual ones of the users may be associated with individual ones of the user records. A user record may define values of the user parameters associated with a given user.

The values of the user parameters may, by way of non-limiting example, specify one or more of: a user name, a group parameter, a user account, a user department, descriptive user content, a to-email, a from-email, a photo, an organization, a workspace, one or more user comments, one or more teams the user belongs to, one or more of the user display settings (e.g., colors, size, project order, task order, other unit of work order, etc.), one or more authorized applications, one or more interaction parameters (e.g., indicating a user is working on/worked on a given unit of work, a given user viewed a given work unit of work, a given user selected a given unit of work, a timeframe a given user last interacted with and/or worked on a given unit of work, a time period that a given unit of work has been idle, and/or other interaction parameters), one or more notification settings, one or more progress parameters, status information for one or more work units the user is associated with (units of work assigned to the user, assigned to other users by the user, completed by the user, past-due date, and/or other information), progress information for one or more business objectives the user is associated with (business objectives owned by the user, of which the user is a collaborator, fulfilled by the user, past-due date, and/or other information), one or more performance/productivity metrics of a given user (e.g., how many units of work the user has completed, how quickly the user completed the units of work, how quickly the user completes certain types of work units, the efficiency of the user, bandwidth of the user, activity level of the user, how many business objectives the user has helped fulfill through their completion of units of work, etc.), application access information (e.g., username/password for one or more third-party applications), one or more favorites and/or priorities, preference information, and/or other information.

The preference information may include user preferences for individual projects (e.g., project preferences) and/or other parts of the collaboration environment. By way of non-limiting illustration, project preferences may include one or more of quantity of the units of work within the individual projects, arrangement of the units of work within the individual projects, dependency of the units of work within the individual projects, assignment of the individual users to the units of work within the individual projects, the roles of the individual users assigned to the units of work within the individual projects, and/or other information.

The work information in the work unit records may include values of one or more work unit parameters. The values of the work unit parameters may be organized in work unit records corresponding to units of work managed, created, and/or assigned within the collaboration environment. A given unit of work may have one or more assignees and/or collaborators working on the given work unit. Units of work may include one or more to-do items, action items, objectives, and/or other units of work one or more users should accomplish and/or plan on accomplishing. Units of work may be created by a given user for the given user and/or created by the given user and assigned to one or more other users. Individual units of work may include one or more of an individual task, an individual sub-task, and/or other units of work assigned to and/or associated with one or more users. Individual units of work may include one or more digital content items. An individual unit of work may include an individual digital content item by virtue of the individual digital content item (and/or a copy or instance thereof) being attached and/or appended thereto. A digital content item may include one or more of an image, a video, an audio file, a PDF, a word document, and/or other digital content items.

In some implementations, units of work created by, assigned to, and/or completed by the users may refer generally to a linking of the units of work with the individual users in the collaboration environment. A unit of work may be linked with a user in a manner that defines one or more relationships between the user and the unit of work. Such a relationship may connote and/or be a result of an action (past, present, and/or future) of the user with respect to the unit of work. Such actions may include one or more of creating a work unit record for a unit of work, being assigned to participate in a unit of work, participating in a unit of work, being granted access to a work unit record of a unit of work, adjusting a value of a work unit parameter of a work unit record of a unit of work, and/or other actions.

Individual sets of work unit records may be defined by a record hierarchy. A record hierarchy may convey individual positions of work unit records (and their corresponding units of work) in the record hierarchy. By way of non-limiting illustration, a position may specify one or more of a work unit record being superior to another work unit record, a work unit record being subordinate to another work unit record, and/or other information. As a result, individual work unit records in the individual sets of work unit records may be subordinate to other individual work unit records in the individual sets of work unit records. For example, a work unit record may define a unit of work comprising a task, and a subordinate work unit record may define a unit of work comprising a sub-task to the task. A record hierarchy may define a relationship between work unit records. A work unit record may have some restrictions placed on it by virtue of having a subordinate work unit record. By way of non-limiting illustration, a work unit record may be restricted from access by one or more users unless and/or until a subordinate work unit record is completed and/or started.

Individual work unit records may include hierarchical information defining a record hierarchy of the individual work unit records. The hierarchical information of a work unit record may include one or more of information identifying other work unit records associated in a record hierarchy the work unit record belongs to, a specification of the position of the work unit record in the hierarchy, restrictions and/or other relationships placed on the work unit record by virtue of its position, and/or other information.

In some implementations, the one or more work unit parameters may include one or more of a work assignment parameter, a work management parameter, work creation parameter, a work unit role parameter, and/or other parameters. The values of the work assignment parameter may describe units of work assigned to the individual users. The values of the work management parameter may describe units of work managed by the individual users. The values of the work creation parameter may describe units of work created by the individual users. The work unit role parameter may characterize individual roles of the individual users with respect to individual units of work. The value of the work unit role parameter may comprise a description and/or title of the role.

In some implementations, values of work unit parameters may include one or more of a unit of work name, a unit of work description, one or more unit of work dates (e.g., a start date, a due date or end date, a completion date, and/or dates), role information, a status parameter (e.g., an update, a hardcoded status update, a completed/incomplete/mark complete, a measured status, a progress indicator, quantity of sub-work units remaining for a given unit of work, measure of urgency, and/or other status parameter), one or more user comment parameters (e.g., permission for who may make comments such as an assignee, an assignor, a recipient, one or more followers, and/or one or more other interested parties; content of the comments; one or more times; presence or absence of the functionality of up-votes; one or more hard-coded responses; and/or other parameters), one or more interaction parameters (e.g., indicating a given unit of work is being worked on/was worked on, a given work unit of work was viewed, a given unit of work was selected, how long the given unit of work has been idle, a last interaction parameter indicating when and what user last interacted with the given unit of work, users that interacted with the given unit of work, quantity and/or content of comments on the unit of work, and/or other interaction parameters indicating sources of the interactions, context of the interactions, content of the interactions and/or time for the interactions), one or more digital content item attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within a given unit of work (e.g., tasks within a project, subtasks within a task, etc.), state of a workspace for a given unit of work (e.g., application state parameters, application status, application interactions, user information, and/or other parameters related to the state of the workspace for a unit of work), one or more performance/productivity metrics for a given unit of work, hierarchical information, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.

The values of the work assignment parameter describing units of work assigned to the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign one or more unit of work to themselves and/or another user. In some implementations, a user may be assigned a unit of work and the user may effectuate a reassignment of the unit of work from the user or one or more other users.

In some implementations, values of the work assignment parameter may indicate that a status parameter of a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, a status of complete for a unit of work may be associated with the passing of an end date associated with the unit of work. In some implementations, a status of “marked complete” may be associated with a user providing input via the collaboration environment at the point in time the user completes the unit of work (which may be before or after an end date).

In some implementations, managing by the environment state component 108 include maintaining queues of the units of work assigned to the users. The queues may be presented to the users in a user interface of the collaboration environment to facilitate access to the units of work via work unit pages. A work unit page for a unit of work may comprise a user interface portion and/or dedicated user interface of the collaboration environment from which users access the unit of work. Individual queues may represent the units of work assigned to individual users organized in an order based on the individual end dates and/or other dates (e.g., start dates) and/or other ordering. Individual queues may be presented in a user interface based on one or more of a list view, a calendar view, and/or other views. The calendar view may be a calendar view by week, by more than one week (e.g., 1^(st) through 15^(th)), by month, by more than one month (e.g., May through July), and/or other calendar views. Units of work may be represented in a calendar view by user interface elements (e.g., icons, calendar entries, etc.).

Project information in project records may define values of project parameters for projects managed within the collaboration environment. An individual project may include an individual set of the units of work. An individual set of units of work of an individual project may be subordinate to the individual project, make up the individual project, and/or otherwise support the individual project. The individual set of units of work may directly facilitate progress toward fulfillment of the individual project. The individual set of units of work may directly contribute to the progress. By way of non-limiting illustration, a connection between the individual set of units of work and a corresponding individual project may be direct in that completion of at least one of the units of work may have a direct impact on progress toward fulfillment of the individual project. The concept of “direct impact” may mean that completion of the at least one unit of work may cause progress toward fulfillment of individual project based on independent action completed and/or started with respect to the at least one unit of work. Accordingly, completion of an individual set of units of work may indicate that the individual project has been completed and/or fulfilled.

The project parameters may characterize one or more projects managed within the collaboration environment and/or via the collaboration environment, and/or the metadata associated with the one or more projects. Individual ones of the projects may be associated with individual ones of the project records. The project information may define values of the project parameters associated with a given project managed within the collaboration environment and/or via the collaboration environment. A given project may have one or more owners and/or one or more collaborators working on the given project. The given project may include one or more units of work assigned to one or more users under the given project heading. In some implementations, projects may include one or more units of work that may directly facilitate progress toward fulfillment of the projects. Accordingly, completion of the set of units of work may directly contribute to progress toward fulfillment of the project. By way of non-limiting illustration, an individual project may be associated with a client and the units of work under the individual project heading may be work directly contributing to the fulfillment of a business relationship with the client.

The values of the project parameters may, by way of non-limiting example, include one or more of: one or more units of work within the project (which may include values of work unit parameters defined by one or more work unit records), role information, one or more user comment parameters (e.g., a creator, a recipient, one or more followers, one or more other interested parties, content, one or more times, upvotes, other hard-coded responses, etc.), a project name, a project description, one or more project dates (e.g., a start date, a due date, a completion date, and/or other project dates), a status and/or progress (e.g., an update, a hardcoded status update, a measured status, quantity of units of work remaining in a given project, completed units of work in a given project, and/or other status parameter), one or more attachments, notification settings, privacy, an associated URL, one or more interaction parameters (e.g., sources of the interactions, context of the interactions, content of the interactions, time for the interactions, and/or other interaction parameters), updates, ordering of units of work within the given project, state of a workspace for a given task within the given project, and/or other information.

Role information may be specified in work unit records and project records. individual roles of the individual users. The role information may specify roles of the users within the units of work and/or the projects. The roles may convey expected contribution of the users in completing and/or supporting the units of work and/or the projects. The individual roles of individual users within the units of work may be specified separately from the individual roles of the individual users within the projects. The project parameters may include a project role parameter characterizing the individual roles of the individual users with respect to individual projects. By way of non-limiting illustration, a first user may have a first role within a first unit of work and a second role within a first project. The first project may include the first unit of work and one or more other units of work.

A role may represent expected contribution of the users in completing and/or supporting the units of work and/or the projects. A role specified with respect to units of work and/or projects may be different from roles traditionally specified with respect to a business organization as a whole (e.g., President, CEO, intern, product designer, legal counsel, etc.). For example, an organization role may be “Product Designer”; a project role may be “Design Lead”; and a role on an individual unit of work may be “Approver.”

A role within a unit of work may be specified based on one or more of a job title, a description of what the user should accomplish and/or plan on accomplishing for the given unit of work, and/or other specifications. By way of non-limiting illustration, a role within a unit of work may include one or more of general assignee, graphic designer, engineer, tester, writer, artist, mechanic, and/or other descriptions.

A role within a project may be specified based on a description of what the user may be supporting and/or plan on supporting for the given project, and/or other specifications. By way of non-limiting illustration, a role within a project may include one or more of owner, design, marketing, copy, legal, engineering, art director, and/or other descriptions. Although the specification of the role in a project may include the same or similar words as the role in a unit of work, the role in the project may enable and/or disable features within the collaboration environment otherwise not available to users of having roles in individual units of work but not at the project level. In some implementations, roles within a project may take on a more supervisory connotation than the roles within the individual units of work.

The objective information in objective records may include values of one or more objective parameters. The values of the objective parameters may be organized in objective records corresponding to business objectives managed, created, and/or owned within the collaboration environment. A given business objective may have one or more collaborators, and/or team members working on the given business objective. Business objectives may include one or more associated units of work and/or projects one or more users should accomplish and/or plan on accomplishing. Business objectives may be created by a given user for the given user and/or created by the given user and assigned to be owned to one or more other users. Individual business objectives may include one or more of an individual goal, an individual sub-goal, and/or other business objectives assigned to be owned by a user and/or associated with one or more users.

The business objectives may be associated with a set of units of work and/or projects that may indirectly facilitate progress toward fulfillment of the business objectives. The set of units of work and/or projects may not directly contribute to the progress. By way of non-limiting illustration, a connection between the set of units of work and/or projects and a corresponding business objective may be indirect in that completion of at least one of the units of work and/or projects may have no direct impact on progress toward fulfillment of the business objective. The concept of “no direct impact” may mean that completion of the at least one unit of work and/or project may not cause progress toward fulfillment of the business objective without independent action outside of the at least one unit of work and/or project. Instead, the fulfillment of the at least one unit of work and/or project may make such independent action more likely (e.g., through coercion, assistance, education, incentivization, reminder, etc.). However, in some implementations, business objectives may be associated with a set of units of work and/or projects that may directly facilitate progress toward fulfillment of the business objectives. Accordingly, completion of the set of units of work and/or projects may directly contribute to the progress toward fulfillment. Business objectives may be associated with an objectives and key result (OKR) goal-setting framework. Business objectives may be specified on one or more of a team basis, organization basis, and/or other specifications. In some implementations, business objectives may be characterized as user objectives. The user objectives may be associated with a set of units of work and/or projects that may indirectly (and/or directly) facilitate progress toward fulfillment of the user objectives. User objectives may be specified on an individual user basis.

Individual objective records may describe individual business objectives and identify sets of individual ones of the work unit records and/or project records that specify the units of work and/or projects as being associated with the individual business objectives.

Individual sets of objective records may be defined by an objective record hierarchy. An objective record hierarchy may convey individual positions of objective records (and their corresponding business objectives) in the objective record hierarchy. By way of non-limiting illustration, a position may specify one or more of an objective record being superior to one or more other objective records, an objective record being subordinate to one or more other objective records, and/or other information. As a result, individual objective records may be subordinate and/or superior to other individual objective records. For example, the objective records may further include a second objective record. The first objective record and the second objective record may be organized by a first objective record hierarchy specifying that the second objective record is subordinate to the first objective record.

An objective record may define a business objective comprising a progress towards fulfillment, and a subordinate objective record may define a business objective comprising a subordinate progress towards fulfillment to the subordinate business objective. An objective record hierarchy may define a relationship between objective records.

Individual objective records may include hierarchical information defining an objective record hierarchy of the individual objective records. The hierarchical information of an objective record may include one or more of information identifying other objective records associated in an objective record hierarchy the objective record belongs to, a specification of the position of the objective record in the hierarchy, other relationships placed on the objective record by virtue of its position, and/or other information.

In some implementations, as a consequence of the objective record hierarchies, the individual business objectives described in the individual objective records that are subordinate to the other individual objective records may be subordinate to the individual business objectives in the other individual objective records.

In some implementations, the one or more objective parameters may include one or more of an objective definition parameter, an objective owner parameter, an objective management parameter, an objective creation parameter, an objective progress parameter, and/or other parameters. The value of the objective definition parameter may describe the particular business objective. The values of the objective owner parameter may describe business objectives assigned to be owned by an individual user. The values of the objective management parameter may describe business objectives managed as collaborators by the individual users. The values of the objective creation parameter may describe business objectives created by the individual users.

In some implementations, the business objectives may be described based on one or more of a business objective name, a business objective description, one or more business objective dates (e.g., a start date, a due date, and/or dates), one or more users associated with a business objective, progress information (e.g., an update, a hardcoded status update, a measured status, a progress indicator, quantity value remaining for a given business objective, completed work units in a given project, and/or other progress information), one or more interaction parameters, notification settings, privacy, an associated URL, one or more custom fields (e.g., priority, cost, stage, and/or other custom fields), and/or other information.

The values of the objective owner parameter describing business objectives owned by the individual users may be determined based on one or more interactions by one or more users with a collaboration environment. In some implementations, one or more users may create and/or assign ownership of one or more business objectives to themselves and/or another user. In some implementations, a user may be assigned to own a business objective and the user may effectuate a reassignment of ownership of the business objective from the user or one or more other users.

Environment state component 108 may be configured to update the environment state information based on the role information and/or other information. By way of non-limiting illustration, the work unit parameters include the work unit role parameter characterizing the individual roles of the individual users with respect to individual units of work. The project parameters may include the project role parameter characterizing the individual roles of the individual users with respect to individual projects. By way of non-limiting illustration, a first value of the work unit role parameter for the first unit of work may specify that the first user has the first role within the first unit of work, and a second value of the project role parameter for the first project specifies the first user as having the second role within the first project.

The user interface component 112 may be configured to effectuate presentation of user interfaces and/or other displays on individual client computing platforms of one or more client computing platforms 104. The user interface component 112 may be configured to effectuate presentation of the collaboration environment as a whole, individual work unit pages, individual project pages, and/or other content. The user interface component 112 may be configured to effectuate presentation of the collaboration environment based on the environment state information so that access, by the users, to the individual units of work and/or the individual projects reflects the roles of the users within the units of work and/or the projects.

In some implementations, presenting the collaboration environment to reflect the roles of the users within the units of work and/or the projects may comprise enabling and/or disabling use of sets of features. By way of non-limiting illustration, individual sets of features may be related to the individual units of work and/or the individual projects based on the roles of the users within the units of work and/or the projects. The individual sets of features related to the individual units of work may be specific to completing and/or supporting specific ones of the individual units of work. The individual sets of features related to the individual projects may be specific to supporting the individual projects. In some implementations, if one or more features are not enabled for a given user, those one or more features may be deemed disabled for the given user. For example, the features enabled for users having a project-level role may be specifically disabled for users having roles within units of work but not at the project level.

In some implementations, the individual sets of features specific to completing and/or supporting the individual units of work may be enabled within individual work unit pages providing access to the individual units of work. The individual work unit pages may comprise a user interface that provide access to and/or otherwise facilitate interaction with a given unit of work. The individual sets of features specific to completing and/or supporting the individual units of work may include one or more of specifying completion status of the individual units of work, communicating with other users linked within the individual units of work, generating meetings with the other users having other roles (e.g., subordinate or superior) within the individual units of work, accessing application programs outside of the collaboration environment, editing the individual units of work, and/or other features.

In some implementations, specifying completion status of the individual units of work may include the ability to change values of the work assignment parameter to indicate a unit of work has changed from “incomplete” to “marked complete” and/or “complete”. In some implementations, specifying completion status of the individual units of work may include the ability to change values of the work assignment parameter to indicate a unit of work has changed from “complete” or “marked complete” to “incomplete”.

In some implementations, communicating with other users linked within the individual units of work may include communicating within individual work unit pages (e.g., adding comments, messages, and/or other communications), communicating within the collaboration environment (e.g., messaging system not tied to a given unit of work), communicating outside of the collaboration environment (e.g., email, SMS, etc.), and/or other considerations. In some implementations, the other users linked within a unit of work may include other users having specific roles within the unit of work.

In some implementations, generating meetings with other users having other roles within the individual units of work may include sending invites to the other users. Sending invites may include selecting meeting participants, proposed date/time for the meeting, setting agenda topics, and/or other functionality. In some implementations, generating meetings with other users may be limited to other users of certain roles within the individual units of work. In some implementations, this may include only generating meetings with users having one or more of a subordinate role, a superior role, a similar role, and/or other types of users. By way of non-limiting illustration, users of a given role within a unit of work may be allowed to generate meetings with their subordinates within the context of the unit of work. Meeting generation may be facilitated by functionality that is integral to the collaboration environment and/or provided through access to an external resource (e.g., third party meeting generation applications).

In some implementations, editing the individual units of work may include one or more of adding, removing, changing, updating, and/or otherwise interacting directly with values of one or more work unit parameters of the individual units of work.

In some implementations, the individual sets of features specific to completing and/or supporting the individual projects may be enabled within individual project pages providing access to the individual projects. The individual sets of features specific to supporting the individual projects may include one or more of communicating with the other users having other roles within the individual projects, communicating with the other users linked to the units of work within the individual projects, generating meetings with the other users having the other roles within the individual projects, generating meetings with the other users linked to the units of work within the individual projects, editing the individual projects, editing the units of work within the individual projects, setting privileges for users having roles within individual units of work that make up the individual projects, and/or other features.

In some implementations, communicating with the other users having other roles within the individual projects may include communicating within individual project pages (e.g., adding comments, messages, and/or other communications), communicating within the collaboration environment (e.g., messaging system not tied to a given project), communicating outside of the collaboration environment (e.g., email, SMS, etc.), and/or other considerations. In some implementations, the other users having other roles within a project may include other users having specific roles within the project. The specific roles may be roles considered subordinate to a given user's role, or superior to the given user's role.

In some implementations, communicating with the other users linked to the units of work within the individual projects may include communicating within individual work unit pages (e.g., adding comments, messages, and/or other communications), communicating within the collaboration environment (e.g., messaging system not tied to a given unit of work), communicating outside of the collaboration environment (e.g., email, SMS, etc.), and/or other considerations. In some implementations, the other users linked within a unit of work may include other users having specific roles within the unit of work.

In some implementations, generating meetings with the other users having the other roles within the individual projects may include sending invites to the other users. Sending invites may include selecting meeting participants, proposed date/time for the meeting, setting agenda topics, and/or other functionality. In some implementations, generating meetings with other users may be limited to other users of certain roles within the individual projects. In some implementations, this may include only generating meetings with users having one or more of a subordinate role within the project, a superior role within the project, a similar role within the project, and/or other types of users. By way of non-limiting illustration, users of a given role within a project may be allowed to generate meetings with other users having other roles within the project but not users who have roles within the units of work but not at the project level.

In some implementations, generating meetings with the other users linked to the units of work within the individual projects may include sending invites to the other users. Sending invites may include selecting meeting participants, proposed date/time for the meeting, setting agenda topics, and/or other functionality. In some implementations, generating meetings with other users may be limited to other users having some linking to one or more of the units of work that make up the project.

In some implementations, editing the individual projects may include one or more of adding, removing, changing, updating, and/or otherwise interacting directly with values of one or more project parameters of the individual projects.

In some implementations, editing the units of work within the individual projects may include one or more of adding, removing, changing, updating, and/or otherwise interacting directly with values of one or more work unit parameters of the individual units of work within the project.

User interface component 112 may be configured to provide access to (e.g., enable) and/or restrict access to (e.g., disable) features for the users based on their roles. User interface component 112 configured to determine whether or not the users have a certain role by querying environment state component 108. In some implementations, responsive to a user having given role in a unit of work and/or project, they may be deemed to have access to, or to be restricted from, one or more features.

By way of non-limiting illustration, a first set of features related to the first unit of work may be enabled for the first user by virtue of having the first role within the first unit of work. The first set of features may be specific to completing and/or supporting the first unit of work. Use of a second set of features related to the first project may be enabled for the first user by virtue of having the second role within the first project. The second set of features may be specific to supporting the first project. By way of non-limiting illustration, the second set of features may facilitate supporting the first unit of work and/or the one or more other units of work in the first project.

In some implementations, the sets of features being enabled and/or disabled may be specific to the roles of the users within the units of work and the projects. By way of non-limiting illustration, use of a third set of features related to the first unit of work may be enabled for a second user by virtue of having the third role within the first unit of work. The third set of features may be different from the first set of features. By way of non-limiting illustration, use of a fourth set of features related to the first project may be enabled for the third user by virtue of having the fourth role within the first project. The fourth set of features may be different from the second set of features.

In some implementations, the environment state component 108 may be configured to define the individual projects based on user records of users assigned particular roles in the individual projects. By way of non-limiting illustration, if an individual projects includes a user of a given role, the project may reflect the preferences of the user. In some implementations, the given role may be “owner” and/or other role. This may be a way to preconfigure a project effectively and automatically at the onset based on the particular user who owns the project and/or otherwise maintains the most control over the project.

User interface component 112 may be configured to obtain user records for the users of a given role within the individual projects. The user records may include preference information specifying project preferences of the users of the given role. The user interface component 112 may be configured to define the individual projects including the users of the given role based on the user records. By way of non-limiting illustration, the individual projects including the users of the given role may reflect the project preferences of the users of the given role at the onset of the individual project. This may provide an automated way to set certain project parameters at the onset to align with certain user's preferences. By way of non-limiting illustration, one or more of a quantity of the units of work within a project may be set, an arrangement of the units of work within a project may be set, dependency of individual ones of the units of work within a project may be set, assignment of the individual users to the units of work within a project may be set, the roles of the individual users assigned to the units of work within a project may be set, and/or other project parameters may be set based on project preferences of a user having a given role at the project level.

In some implementations, environment state information may be updated as users continue to interact with the collaboration environment via the user interfaces over time. The environment state component 108 may store and/or archive the environment state information periodically and/or based on user request to archive. In some implementations, the environment state component 108 may store historical environment state information specifying historical user information, historical work information, historical project information, historical objective information, user interaction history, historical role information, and/or other information.

In some implementations, user interface component 112 may be configured to obtain input information and/or other information. The input information may convey user input into a user interface presented on the client computing platform(s) 104. A set of user interface elements may be provided on the user interface to facilitate the user input and/or other user interaction with the user interface. The user interface elements may include one or more of text input fields, drop down menus, check boxes, display windows, virtual buttons, and/or other elements configured to facilitate user interaction. The user input may include roles of users within individual units of work and/or projects.

FIG. 3 illustrates a user interface 300, in accordance with one or more implementations. The user interface 300 may display a project overview graphical user interface 301 for a project, referred to as “Project X.” The project overview graphical user interface 301 for Project X may include a set of interface elements displaying the values of one or more of the project parameters of Project X and/or values of one or more of the work unit parameters of the units of work making up Project X. The user interface elements may convey information including one or more of one or more users having one or more roles at the project level, one or more units of work that make up the project, one or more users having one or more roles in the one or more units of work that make up the project, and/or other information. By way of non-limiting illustration, a first user interface element 302 may indicate that a first user (e.g., User A) has a first role 304 (e.g., owner) within Project X; a second user interface element 306 may indicate that a second user (e.g., User B) has a second role 308 (e.g., engineer) within Project X; and/or a third user interface element 310 may indicate that a third user (e.g., User C) has a third role 312 (e.g., marketing) within Project X. Individual ones of the first user, second user, and/or third user may be granted certain access privileges to Project X and/or one or more units of work that make up Project X that reflects their roles in Project X.

The one or more units of work that may make up Project X may include a first unit of work represented by a fourth user interface element 315, a second unit of work represented by a fifth user interface element 319, and/or a third unit of work represented by a sixth user interface element 323. The second user interface element 306 may indicate that the second user (e.g., User B) has a fourth role 316 (e.g., tester) within the first unit of work; a seventh user interface element 318 may indicate that a fourth user (e.g., User X) has a fifth role 320 (e.g., mechanic) within the second unit of work; and/or an eighth user interface element 322 may indicate that a fifth user (e.g., User Y) has a sixth role 324 (e.g., designer) within the third unit of work. Individual ones of the second user, fourth user, and/or fifth user may be granted certain access privileges to individual units of work that reflects their roles in the individual units of work.

Referring back to FIG. 1 , in some implementations, server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network 116 such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platform(s) 104, and/or external resources 126 may be operatively linked via some other communication media.

A given client computing platform may include one or more processors configured to execute computer program components. The computer program components may be configured to enable an expert or user associated with the given client computing platform to interface with system 100 and/or external resources 126, and/or provide other functionality attributed herein to client computing platform(s) 104. By way of non-limiting example, the given client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a tablet computing platform, a NetBook, a Smartphone, a gaming console, and/or other computing platforms.

External resources 126 may include sources of information outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 126 may be provided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors 130, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network 116 and/or other computing platforms. Illustration of server(s) 102 in FIG. 1 is not intended to be limiting. Server(s) 102 may include a plurality of hardware, software, and/or firmware components operating together to provide the functionality attributed herein to server(s) 102. For example, server(s) 102 may be implemented by a cloud of computing platforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media that electronically stores information. The electronic storage media of electronic storage 128 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 128 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 128 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 128 may store software algorithms, information determined by processor(s) 130, information received from server(s) 102, information received from client computing platform(s) 104, and/or other information that enables server(s) 102 to function as described herein.

Processor(s) 130 may be configured to provide information processing capabilities in server(s) 102. As such, processor(s) 130 may include one or more of a digital processor, a physical processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 130 is shown in FIG. 1 as a single entity, this is for illustrative purposes only. In some implementations, processor(s) 130 may include a plurality of processing units. These processing units may be physically located within the same device, or processor(s) 130 may represent processing functionality of a plurality of devices operating in coordination. Processor(s) 130 may be configured to execute components 108, 110, 112, and/or other components. Processor(s) 130 may be configured to execute components 108, 110, and/or 112, and/or other components by software; hardware; firmware; some combination of software, hardware, and/or firmware; and/or other mechanisms for configuring processing capabilities on processor(s) 130. As used herein, the term “component” may refer to any component or set of components that perform the functionality attributed to the component. This may include one or more physical processors during execution of processor readable instructions, the processor readable instructions, circuitry, hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, and/or 112 are illustrated in FIG. 1 as being implemented within a single processing unit, in implementations in which processor(s) 130 includes multiple processing units, one or more of components 108, 110, and/or 112 may be implemented remotely from the other components. The description of the functionality provided by the different components 108, 110, and/or 112 described below is for illustrative purposes, and is not intended to be limiting, as any of components 108, 110, and/or 112 may provide more or less functionality than is described. For example, one or more of components 108, 110, and/or 112 may be eliminated, and some or all of its functionality may be provided by other ones of components 108, 110, and/or 112. As another example, processor(s) 130 may be configured to execute one or more additional components that may perform some or all of the functionality attributed below to one of components 108, 110, and/or 112.

FIG. 2 illustrates a method 200 to facilitate interaction with a collaboration environment based on assignment of project-level roles, in accordance with one or more implementations. The operations of method 200 presented below are intended to be illustrative. In some implementations, method 200 may be accomplished with one or more additional operations not described, and/or without one or more of the operations discussed. Additionally, the order in which the operations of method 200 are illustrated in FIG. 2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 200 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 200.

An operation 202 may manage environment state information maintaining a collaboration environment, and/or other information. The collaboration environment may be configured to facilitate interaction by users with the collaboration environment. The environment state information may include one or more of work unit records, project records, and/or other records. The work unit records may include values for work unit parameters associated with units of work managed, created, and/or assigned within the collaboration environment. The project records may include values for project parameters associated with projects managed within the collaboration environment. An individual project may include an individual set of the units of work. Operation 202 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108 (shown in FIG. 1 and described herein), in accordance with one or more implementations.

An operation 204 may obtain role information specifying roles of the users within the units of work and the projects. The roles may convey expected contribution of the users in completing and/or supporting the units of work and the projects. The individual roles of individual users within the units of work may be specified separately from the individual roles of the individual users within the projects. By way of non-limiting illustration, a first user may have a first role within a first unit of work and a second role within a first project. The first project may include the first unit of work and one or more other units of work. Operation 204 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to role management component 110 (shown in FIG. 1 and described herein), in accordance with one or more implementations.

An operation 206 may update the environment state information based on the role information and/or other information. The work unit parameters may include a work unit role parameter characterizing the individual roles of the individual users with respect to individual units of work. The project parameters may include a project role parameter characterizing the individual roles of the individual users with respect to individual projects. By way of non-limiting illustration, a first value of the work unit role parameter for the first unit of work may specify that the first user has the first role within the first unit of work, and a second value of the project role parameter for the first project may specify that the first user has the second role within the first project. Operation 206 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to environment state component 108 (shown in FIG. 1 and described herein), in accordance with one or more implementations.

An operation 208 may effectuate presentation of the collaboration environment based on the environment state information so that access, by the users, to the individual units of work and the individual projects reflects the roles of the users within the units of work and the projects. Operation 208 may be performed by one or more hardware processors configured by machine-readable instructions including a component that is the same as or similar to user interface component 112 (shown in FIG. 1 and described herein), in accordance with one or more implementations.

Although the present technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the technology is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present technology contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation. 

What is claimed is:
 1. A system configured to facilitate interaction with a collaboration environment based on assignment of roles, the system comprising: one or more physical processors configured by machine-readable instructions to: manage, by a server, environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by a first user with the collaboration environment, wherein the first user interacts with the collaboration environment via a first remotely located client computing platform communicating with the server over one or more Internet connections, the environment state information including a first project record for a first project, the first project being associated with a first unit of work and one or more other units of work; obtain, by the server, role information specifying roles of the first user, the role information specifying the first user has a first role within the first unit of work and concurrently has a second role within the first project; generate, by the server, information defining a user interface of the collaboration environment; and effectuate communication of the information defining the user interface of the collaboration environment to the first remotely located client computing platform over the one or more Internet connections to cause the first remotely located client computing platform to present the user interface so that the first user's ability to interact with a work unit record of the first unit of work and the first project record of the first project is made dependent on the roles of the first user, such that use of a first set of features related to interacting with the first work unit record is enabled for the first user by virtue of having the first role within the first unit of work, and use of a second set of features related to interacting with the first project record is enabled for the first user by virtue of having the second role within the first project.
 2. The system of claim 1, wherein one or more features in the first set of features are specific to completing and/or supporting the first unit of work, and one or more features in the second set of features are specific to supporting the first project.
 3. The system of claim 2, wherein the first set of features are enabled within a first work unit page providing access to the first work unit record.
 4. The system of claim 3, wherein the first set of features includes one or more of specifying completion status, communicating with other users, or generating meeting requests.
 5. The system of claim 2, wherein the second set of features are enabled within a project page providing access to the first project record.
 6. The system of claim 5, wherein the second set of features include one or more of communicating with other users via the project page, generating meetings requests via the project page, or editing the project page.
 7. The system of claim 6, wherein the second set of features include editing the project page.
 8. The system of claim 1, wherein: use of a third set of features related to interacting with the first work unit record is enabled for a second user by virtue of the second user having a third role within the first unit of work, the third set of features being different from the first set of features; and use of a fourth set of features related to interacting with the first project record is enabled for the third user by virtue of the third user concurrently having a fourth role within the first project, the fourth set of features being different from the second set of features.
 9. The system of claim 1, wherein the one or more physical processors are further configured by the machine-readable instructions to obtain a first user record for the first user.
 10. The system of claim 9, wherein the first user record includes preferences of the first user.
 11. A method to facilitate interaction with a collaboration environment based on assignment of project-level roles, the method comprising: managing, by a server, environment state information maintaining a collaboration environment, the collaboration environment being configured to facilitate interaction by a first user with the collaboration environment, wherein the first user interacts with the collaboration environment via a first remotely located client computing platform communicating with the server over one or more Internet connections, the environment state information including a first project record for a first project, the first project being associated with a first unit of work and one or more other units of work; obtaining, by the server, role information specifying roles of the first user, the role information specifying the first user has a first role within the first unit of work and concurrently has a second role within the first project; generating, by the server, information defining a user interface of the collaboration environment; and effectuating communication of the information defining the user interface of the collaboration environment to the first remotely located client computing platform over the one or more Internet connections to cause the first remotely located client computing platform to present the user interface so that the first user's ability to interact with a work unit record of the first unit of work and the first project record of the first project is made dependent on the roles of the first user, including enabling use of a first set of features related to interacting with the first work unit record for the first user by virtue of having the first role within the first unit of work, and enabling use of a second set of features related to interacting with the first project record for the first user by virtue of having the second role within the first project.
 12. The method of claim 11, wherein one or more features in the first set of features are specific to completing and/or supporting the first unit of work, and one or more features in the second set of features are specific to supporting the first project.
 13. The method of claim 12, wherein the first set of features are enabled within a first work unit page providing access to the first work unit record.
 14. The method of claim 13, wherein the first set of features includes one or more of specifying completion status, communicating with other users, or generating meeting requests.
 15. The method of claim 12, wherein the second set of features are enabled within a project page providing access to the first project record.
 16. The method of claim 15, wherein the second set of features include one or more of communicating with other users via the project page, generating meetings requests via the project page, or editing the project page.
 17. The method of claim 16, wherein the second set of features include editing the project page.
 18. The method of claim 11, further comprising: enabling use of a third set of features related to interacting with the first work unit record for a second user by virtue of the second user having a third role within the first unit of work, the third set of features being different from the first set of features; and enabling use of a fourth set of features related to interacting with the first project record for the third user by virtue of the third user concurrently having a fourth role within the first project, the fourth set of features being different from the second set of features.
 19. The method of claim 11, wherein further comprising obtaining a first user record for the first user.
 20. The method of claim 19, wherein the first user record includes preferences of the first user. 